Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable caret events in all terminal programs #10118

Merged
merged 1 commit into from
Aug 22, 2019

Conversation

codeofdusk
Copy link
Contributor

@codeofdusk codeofdusk commented Aug 19, 2019

Link to issue number:

Closes #1348.
Related to #9933, #9986.

Summary of the issue:

In Mintty, the last character of the prompt is read when quickly deleting text, just as in Windows Console (see this comment and the "summary of the issue" section in #9986).

Description of how this pull request fixes the issue:

This PR disables caret events for all Terminal objects by overriding NVDAObjects.behaviors.Terminal._get_caretMovementDetectionUsesEvents, instead of only Windows Console like in #9986.

Testing performed:

Tested the steps to reproduce from #1348 in PuTTY and observed that extra characters are no longer read. Verified that caret movement and backspace reporting are still functional in PuTTY after the changes.

Known issues with pull request:

None.

Change log entry:

None (py3 regression).

@codeofdusk
Copy link
Contributor Author

@feerrenrut
Copy link
Contributor

You have talked about the testing in Putty and the intended changed in behavior in Mintty, but this change affects all terminals. What have you done to verify there are no regressions elsewhere (cmd, older OS)?

@lukaszgo1
Copy link
Contributor

When testing for regressions don't forget SSH clients such as SecureCRT, Tera Term.

@LeonarddeR
Copy link
Collaborator

Note that this pr restores the behaviour of terminals to the situation before #9933, so I don't think we have to be afraid of any major regressions here.

@codeofdusk
Copy link
Contributor Author

Note that this pr restores the behaviour of terminals to the situation before #9933, so I don't think we have to be afraid of any major regressions here.

Correct.

@feerrenrut feerrenrut merged commit 4d384fa into nvaccess:master Aug 22, 2019
@nvaccessAuto nvaccessAuto added this to the 2019.3 milestone Aug 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

NVDA doesn't announce typed characters in putty
5 participants